Conversation
YOU54F
force-pushed
the
feat/remove_rust_tools
branch
from
832a1f3 to
591cdd5
Compare
4 tasks
JP-Ellis
approved these changes
Mar 16, 2026
Contributor
JP-Ellis
left a comment
JP-Ellis
left a comment
There was a problem hiding this comment.
Make complete sense!
Should we perhaps add an admonition in the root README redirecting users in case they are looking for the Rust tools?
E.g.:
Note
We have recently removed the bundled Rust tools from the Pact (Ruby) standalone. You can find the Rust tools at pact-foundation/pact-cli.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
in prep as part of pact-foundation/roadmap#127
pact.rbwhich is a consolidated entry point to the ruby binaries, this avoids overlap if legacy tools are loaded into the same path as the new pact-cli, which is suggested to be named aspacton the users machine